Thanks 👍

To me this looks fine to apply this by default, as content images are less important to load compared to other images (like layout images)

Later we'll introduce an official core <Img> component in Docusaurus and it's a common practice to add some IntersectionObserver logic to make it load eagerly images that are close to entering the viewport (similar to links/idealImage)

Note users that want to disable lazy loading can still disable this thanks to a remark plugin. It's not very convenient/elegant but it's just erasing loading="lazy" from the image jsx string.

I think we can ship this by default and see if anyone complains, to eventually revert or provide an option.

My only concern: do we want lazy loading for images we couldn't compute width/height? Not sure when this happens but it may lead to annoying layout shifts as the user scrolls down.

Any opinion @Josh-Cena ?

Let's do this! Later in #5999 we can try to make it configurable